This PR introduces many things, but mainly:

• supabase/ folder with supabase support for local development (CURRENTLY NOT IMPLEMENTED WITH DOCKER COMPOSE)
• conference, committee, etc DB models on the first migration file.
• auth/, access/ and core/ domains on the backend
• rework some backend code to feature Depends Dep. Injection instead of a Factory pattern
  • this also adds a new dep.py file for dependency injections on the backend
• protected session routes (create planned session, activate planned session, websocket session now sends a token as the first message to check if user has a committee assignment, etc)
• additional layer for the backend architecture, now the separation is:
  views: API endpoints
  service: app orchestration, data validation, etc
  repository: DB queries with raw SQL
• many changes on current code (like schemas, etc)
• do keep in mind conference/ domain is not implemented yet. but seeded data exists on the database

as for the frontend work:

• add supabase client. We'll use this to connect to supabase auth api and login users
• context for storing user data (access tokens, refresh tokens, etc)
• apiFetch wrapper to send tokens with each request to the backend endpoints
• many fixes
• mostly conscious vibe coding

What remains:

• test overall authing on session page
• add a conference/ domain + endpoints on the backend and proper pages on the frontend
• improve current session creation
• improve session snapshot save to database
• document code
• replace delegation with representation
• improve frontend pages
• do integration tests for the session part